chore: auto-update QPK_PIN and constraints.txt#161
Conversation
Pigbibi
force-pushed
the
auto/qpk-pin-update
branch
2 times, most recently
from
647a1db to
5ae014c
Compare
github-actions
Bot
force-pushed
the
auto/qpk-pin-update
branch
2 times, most recently
from
4f71ee3 to
1583738
Compare
github-actions
Bot
force-pushed
the
auto/qpk-pin-update
branch
from
1583738 to
14620ff
Compare
Co-Authored-By: Codex <noreply@openai.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 99abdc947c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| src/quant_platform_kit/longbridge/portfolio.py | ||
| src/quant_platform_kit/notifications/__init__.py | ||
| src/quant_platform_kit/notifications/_email.py | ||
| src/quant_platform_kit/notifications/_redaction.py |
There was a problem hiding this comment.
Including this generated egg-info change in the auto pin PR means the merge changes paths not covered by .github/workflows/update-qpk-pin.yml's paths-ignore list, which only ignores QPK_PIN, constraints.txt, docs, and Markdown files. On the push that lands this PR, the Update QPK Pin workflow will run again and open another pin update for the merge SHA even though no QPK source changed, so keep the generated PR limited to the ignored pin files or ignore egg-info outputs.
Useful? React with 👍 / 👎.
| # Auto-updated by update-qpk-pin.yml on every push to QPK main. | ||
|
|
||
| quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@b0eacd2fe4884f7f2447b704a232e9a121f396c4 | ||
| quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@b9a7df85cfc848cebcc3aa6e1d77ec34ca7611ab |
There was a problem hiding this comment.
This now constrains the shared QPK dependency to b9a7df8, but the strategy repos referenced by the same constraints.txt still declare quant-platform-kit @ ...@b0eacd2 in their pyproject.toml at the pinned refs I checked (UsEquityStrategies@6568c315, HkEquityStrategies@08e20a59, CnEquityStrategies@ffbdf730, and CryptoStrategies@8039dddd). Any normal dependency-resolving install using these constraints, unlike the workflow’s --no-deps dry-run, will have to satisfy both direct URL pins and fail resolution instead of producing the advertised compatible stack.
Useful? React with 👍 / 👎.
1 participant
Automated update of QPK_PIN and dependency constraint SHAs.
Compatibility checks passed ✅ — all downstream-critical QPK modules verified importable.
Updated SHAs:
da921b4d0fdf2b4c8ce6e29539cdccf0c89d893e🤖 Generated with Claude Code